Replies: 9 comments 8 replies
-
|
Having the same issue with GitHub Actions. |
Beta Was this translation helpful? Give feedback.
-
|
Has the same issue while connecting to Infura ETH Mainet public node |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here with Filecoin |
Beta Was this translation helpful? Give feedback.
-
|
That seems like a strange error to come out of ethers. I don’t think that is something it should log anywhere. Is there any more details as to what is not working? Does AWS lambda have a custom fetch? Is it using the lib.esm or lib.commonjs? Or is it using one of the dist files? |
Beta Was this translation helpful? Give feedback.
-
|
I found a reason. My problem is reffered to Filecoin EVM. The JsonRpcProvider is set up after first request and i were sending a get_logs request with 'fromBlock' 0. Ethers v6 did not provide me an error respnse, only code 500. But ethers v5 told me that "bad tipset height: lookbacks of more than 24h0m0s are disallowed". So the request was failed and provider has not been setup. I made a shorter interval for get_logs so now everything works. So what i suggest is to check the first request that you make from JsonRpcProvider |
Beta Was this translation helpful? Give feedback.
-
|
Can you provide me with a URL and the request? That way I can reproduce it and figure out what reflex to add to detect this type of error. Every network and backend has their own custom error strings, so it’s a constant arms race to add them all. :) |
Beta Was this translation helpful? Give feedback.
-
|
I got this error, too. I found this error is after this error Maybe there are some relationship between them. |
Beta Was this translation helpful? Give feedback.
-
|
Can you provide basic reproduction steps? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same error, it's occured after i try to request with non-valid provider, and ethers want to reconnect this provider -> error in loop |
Beta Was this translation helpful? Give feedback.
-
|
I had something similar actually, where my env vars were not being read and hence the rpc was |
Beta Was this translation helpful? Give feedback.
-
|
In my case ,i use tenderly fork rpc and get this error. I found that JsonRpcProvider will try to send eth_chainId and eth_getBlockByNumber together in one request ,which is not supported by tenderly rpc(only single method batches are supported). So I fixed this by disabling batch requests as follows. |
Beta Was this translation helpful? Give feedback.
-
|
That’s really helpful to know. Thanks. I may add some logic to the provider then to automatically prevent that for tenderly. |
Beta Was this translation helpful? Give feedback.
-
|
I suggest directly displaying the error message returned by the server to the user instead of showing |
Beta Was this translation helpful? Give feedback.
-
|
I had same issue with a private network this solved my issue for ethers v6, thank you so much. |
Beta Was this translation helpful? Give feedback.
-
|
This helped me. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Obvious behavior, but i changed "any" in v6 provider |
Beta Was this translation helpful? Give feedback.
-
|
I was also having excessive logs of Before: for (const rpcURL of chain.rpc) {
try {
const provider = rpcURL.startsWith('http')
? new JsonRpcProvider(rpcURL)
: new WebSocketProvider(rpcURL);
// Race the RPC call with a timeout
const bytecode = await Promise.race([
provider.getCode(address),
rejectInMs(RPC_TIMEOUT, rpcURL),
]);
return bytecode;
} catch (err) {
console.log(err);
continue;
}
}After: for (const rpcURL of chain.rpc) {
const provider = rpcURL.startsWith('http')
?new JsonRpcProvider(rpcURL)
: new WebSocketProvider(rpcURL);
// If the provider is not working, skip it
try {
await provider._detectNetwork();
} catch (err) {
console.log(err)
continue;
}
} |
Beta Was this translation helpful? Give feedback.
-
Hello,
I have a strange issue with Ethers in my AWS Lambda setup. Basically, I use lambda to get some Price Oracle data and return it.
I Instantiate the provider in such way:
Sometimes when I call a function GET request multiple times at the same time, some of the executions last long and I'm aborting the request and the last log that I see from the Lambda is:
JsonRpcProvider failed to startup; retry in 1sI don't know why it fails and how to solve that.
EDIT: Adding some more info
Lambda is timing out after 15 min. I see no more logs after the (single) one that I shared.
Beta Was this translation helpful? Give feedback.
All reactions